Reviewing files that changed from the base of the PR and between e673d70 and e20de01.

• package-lock.json is excluded by !**/package-lock.json

• .gitignore (1 hunks)
• Dockerfile (2 hunks)
• deploy_prod.sh (1 hunks)
• entrypoint.sh (1 hunks)
• package.json (1 hunks)
• pythonkr_backend/fixtures.json (1 hunks)
• pythonkr_backend/theme/static_src/tailwind.config.js (1 hunks)

deploy_prod.sh (1)

25-28:

❓ Verification inconclusive

Enforce robust execution and verify Node.js availability

• Add set -euo pipefail to exit on errors.
• Check that node is installed before running npm install to prevent silent failures.
• Ensure package.json resides in python.or.kr for npm install to work.

 #!/usr/bin/env bash
+set -euo pipefail
 PID_FILE="/home/pk/pk.pid"
 # ...
 cd python.or.kr
+command -v node >/dev/null 2>&1 || { echo "Node.js not found"; exit 1; }
 npm install
 source .venv/bin/activate

Please confirm the production host environment has Node.js installed or adjust this script to install the required runtime.

---

Let's inspect the deployment script and its context to confirm the suggestions:

---

🏁 Script executed:

#!/usr/bin/env bash
set -e
# Locate deploy_prod.sh
SCRIPT_PATH=$(fd --hidden deploy_prod.sh | head -n1)
echo "Using: $SCRIPT_PATH"
# Show the first 30 lines and lines 20–40 to view shebang, env settings, and cd usage
sed -n '1,30p' "$SCRIPT_PATH"
echo "----"
sed -n '20,40p' "$SCRIPT_PATH"

Length of output: 1236

---

🏁 Script executed:

#!/usr/bin/env bash
# Verify that package.json exists in python.or.kr
if [ -d python.or.kr ]; then
  find python.or.kr -maxdepth 1 -type f -name 'package.json' -print || echo "No package.json found in python.or.kr"
else
  echo "Directory python.or.kr not found"
fi

# Check Node.js availability in this environment
if command -v node >/dev/null 2>&1; then
  echo "Node.js is installed: $(node -v)"
else
  echo "Node.js not found"
fi

Length of output: 198

---

Enforce robust execution and verify Node.js availability

• Add set -euo pipefail at the top to fail fast on errors.
• Confirm node is installed (we detected Node.js v24.1.0).
• Ensure the python.or.kr directory exists on the production host and contains a valid package.json before running npm install.

Suggested diff in deploy_prod.sh:

 #!/usr/bin/env bash
+set -euo pipefail

 cd ~/
 source .env
 cd python.or.kr
+command -v node >/dev/null 2>&1 || { echo "Node.js not found"; exit 1; }
 npm install
 source .venv/bin/activate
 uv sync
 cd pythonkr_backend
 …  

Please verify on your production server that python.or.kr is the correct path and that package.json is present.

pythonkr_backend/theme/static_src/tailwind.config.js (1)

54-55: Consolidated plugins array is correct
You’ve removed the nested duplication and now declare all three plugins—forms, typography, and aspect-ratio—exactly once in the top-level plugins array. This ensures Tailwind will load them as expected without configuration conflicts.

pythonkr_backend/fixtures.json (1)

20-27: Add Wagtail site fixture
The new "wagtailcore.site" entry correctly defines your primary site—setting hostname, port, an empty site_name, root_page: 3 (which matches the later page with pk=3), and is_default_site: true. This aligns with Wagtail’s site configuration requirements. Ensure no other site fixture is marked as default and that your Django settings reference this hostname and port appropriately.